Update data-platform-workflows to v29 (major) - autoclosed #703
+10
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v24.0.6
->v29.0.1
v24.0.6
->v29.0.1
v24.0.6
->v29.0.1
v24.0.6
->v29.0.1
v24.0.6
->v29.0.1
Release Notes
canonical/data-platform-workflows (allure-pytest-collection-report)
v29.0.1
Compare Source
What's Changed
Full Changelog: canonical/data-platform-workflows@v29.0.0...v29.0.1
v29.0.0
Compare Source
What's Changed
Full Changelog: canonical/data-platform-workflows@v28...v29.0.0
Breaking changes
matrix (e.g. using different
path-to-charm-directory
inputs), theartifact-prefix
output will be identical. This is to workaround anissue where if
needs.build.outputs.artifact-prefix
is used on abuild
job that used a matrix, GitHub picks one of outputs from thematrix items as the output
name in the git tag for the revision, if the path to charm/snap
directory is not
.
create-github-release
input renamed tocreate-git-tags
and nowonly git tags are created instead of tags & github release. GitHub
releases should be used for release notes for stable releases and GitHub
releases should be per-repository, not per-charm
v28.0.0
Compare Source
What's Changed
Full Changelog: canonical/data-platform-workflows@v27...v28.0.0
v27.0.0
Compare Source
What's Changed
Full Changelog: canonical/data-platform-workflows@v26...v27.0.0
v26.0.3
Compare Source
What's Changed
architectures
parsing by @carlcsaposs-canonical in https://github.com/canonical/data-platform-workflows/pull/269Full Changelog: canonical/data-platform-workflows@v26.0.2...v26.0.3
v26.0.2
Compare Source
What's Changed
Full Changelog: canonical/data-platform-workflows@v26.0.1...v26.0.2
v26.0.1
Compare Source
What's Changed
Full Changelog: canonical/data-platform-workflows@v26.0.0...v26.0.1
v26.0.0
Compare Source
What's Changed
Full Changelog: canonical/data-platform-workflows@v25...v26.0.0
Breaking changes
pytest-operator-cache
(which overridesops_test.build_charm
from pytest-operator) now assumes 22.04 baseDeprecation notice
pytest-operator-cache
is deprecated & will be removed in a future releasev25.0.0
Compare Source
What's Changed
Full Changelog: canonical/data-platform-workflows@v24...v25.0.0
Configuration
📅 Schedule: Branch creation - "after 1am and before 3am every weekday" in timezone Etc/UTC, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.